home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93a.txt
/
000101_icon-group-sender _Thu Apr 1 12:13:34 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-04-21
|
1KB
Received: by cheltenham.cs.arizona.edu; Thu, 1 Apr 1993 11:39:45 MST
Date: Thu, 1 Apr 93 12:13:34 EST
From: Paul_Abrahams@MTS.cc.Wayne.edu
To: icon-group@cs.arizona.edu
Message-Id: <616446@MTS.cc.Wayne.edu>
Subject: Error level from MSDOS Icon
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
Here's a minor but annoying problem that shouldn't be too hard to fix at
the next update of MSDOS Icon. If there isn't enough extended memory for
icont to operate, it quits (as I would expect it to). However, if
stderr has been redirected to a file, the generated error messages never
make it to that file, probably because stderr hasn't been closed
properly. In addition, the error level isn't set nonzero.
I came across this behavior because I was setting up an automatic call
to Icon from an editor. There wasn't enough extended memory but all the
indications of the problem were lost (since the editor didn't display the
execution screen). The editor thought that icont had ended normally and
had produced no error file.
I'd be quite happy if icont merely set the error level nonzero if it
aborts because of insufficient memory or a similar condition. I
wouldn't want it to set the error level nonzero just because the source
program has errors.
Paul Abrahams